Content selection associated with webview browsers

ABSTRACT

Methods, systems, and apparatus include computer programs encoded on a computer-readable storage medium for delivering content. A method includes: identifying a webview; providing a script for execution when the webview is initiated, the script causing a device associated with the webview to retrieve a unique identifier associated with the device, encode the unique identifier, construct a URL that includes an advertising system domain and the encoded unique identifier, and pass the encoded unique identifier to the advertising system; passing a cookie for the advertising domain back to the webview for inclusion in the cookie space of the webview; storing information related to interactions of a user of the device when accessing content through different browsers or applications so as to unify the cookie spaces of the different browsers; identifying a request for content as being associated with the device; and using the information to determine content for delivery.

BACKGROUND

This specification relates to information presentation.

The Internet provides access to a wide variety of resources. Forexample, video and/or audio files, as well as web pages for particularsubjects or particular news articles, are accessible over the Internet.Access to these resources presents opportunities for other content(e.g., advertisements) to be provided with the resources. For example, aweb page can include slots in which content can be presented. Theseslots can be defined in the web page or defined for presentation with aweb page, for example, along with search results.

Slots can be allocated to content sponsors through a reservation systemor an auction. For example, content sponsors can provide bids specifyingamounts that the sponsors are respectively willing to pay forpresentation of their content. In turn, a reservation can be made or anauction can be performed, and the slots can be allocated to sponsorsaccording, among other things, to their bids and/or the relevance of thesponsored content to content presented on a page hosting the slot or arequest that is received for the sponsored content.

SUMMARY

In general, one innovative aspect of the subject matter described inthis specification can be implemented in methods that include a methodfor expanding a cookie space associated with a webview. A methodincludes: identifying a webview, the webview being an embedded browserand associated with a cookie space and a path definition that defines apublisher website that is to be loaded by the webview; providing ascript for execution when the webview is initiated, the script causing aresident device associated with the webview to retrieve a uniqueidentifier associated with the resident device, encode the uniqueidentifier, construct a URL that includes an advertising domain of anadvertising system and the encoded unique identifier, and pass theencoded unique identifier to the advertising system; responsive toreceipt of the encoded unique identifier by the advertising system,passing a cookie for the advertising domain back to the webview forinclusion in the cookie space of the webview; storing, in a repositoryof the advertising system and in association with the unique identifier,information related to interactions of a user of the resident devicewhen accessing content on the web through different browsers orapplications including information related to interactions with two ormore of the webview; a second, different webview on the resident device;a browser on the resident device; or an application on the residentdevice so as to unify the cookie spaces of the different browsers;identifying a request for content as being associated with the residentdevice; and using the information to determine content for deliveryresponsive to the request.

In general, another aspect of the subject matter described in thisspecification can be implemented in computer program products. Acomputer program product is tangibly embodied in a computer-readablestorage device and comprises instructions. The instructions, whenexecuted by a processor, cause the processor to: identify a webview, thewebview being an embedded browser and associated with a cookie space anda path definition that defines a publisher website that is to be loadedby the webview; provide a script for execution when the webview isinitiated, the script causing a resident device associated with thewebview to retrieve a unique identifier associated with the residentdevice, encode the unique identifier, construct a URL that includes anadvertising domain of an advertising system and the encoded uniqueidentifier, and pass the encoded unique identifier to the advertisingsystem; responsive to receipt of the encoded unique identifier by theadvertising system, pass a cookie for the advertising domain back to thewebview for inclusion in the cookie space of the webview; store, in arepository of the advertising system and in association with the uniqueidentifier, information related to interactions of a user of theresident device when accessing content on the web through differentbrowsers or applications including information related to interactionswith two or more of the webview; a second, different webview on theresident device; a browser on the resident device; or an application onthe resident device so as to unify the cookie spaces of the differentbrowsers; identify a request for content as being associated with theresident device; and use the information to determine content fordelivery responsive to the request.

In general, another aspect of the subject matter described in thisspecification can be implemented in systems. A system includes one ormore processors and one or more memory elements including instructions.The instructions, when executed, cause the one or more processors to:identify a webview, the webview being an embedded browser and associatedwith a cookie space and a path definition that defines a publisherwebsite that is to be loaded by the webview; provide a script forexecution when the webview is initiated, the script causing a residentdevice associated with the webview to retrieve a unique identifierassociated with the resident device, encode the unique identifier,construct a URL that includes an advertising domain of an advertisingsystem and the encoded unique identifier, and pass the encoded uniqueidentifier to the advertising system; responsive to receipt of theencoded unique identifier by the advertising system, pass a cookie forthe advertising domain back to the webview for inclusion in the cookiespace of the webview; store, in a repository of the advertising systemand in association with the unique identifier, information related tointeractions of a user of the resident device when accessing content onthe web through different browsers or applications including informationrelated to interactions with two or more of the webview; a second,different webview on the resident device; a browser on the residentdevice; or an application on the resident device so as to unify thecookie spaces of the different browsers; identify a request for contentas being associated with the resident device; and use the information todetermine content for delivery responsive to the request.

These and other implementations can each optionally include one or moreof the following features. The script can be configured to make a firstcall to the advertising system, the first call including the encodedunique identifier and an address for the advertising domain, andresponsive to the first call, receive the cookie from the advertisingsystem for inclusion in the cookie space associated with the webview.The advertising system can be configured to, responsive to receipt ofthe first call, provide a response and drop the cookie of theadvertising system in the cookie space associated with the webview. Theresponse can include a tracking pixel. The response can be an emptyresponse which includes no renderable content. The script can beconfigured to make a second, different call after receipt of the cookieof the advertising system, the second call to the publisher website toretrieve content from the publisher website for inclusion in thewebview. The publisher website can include one or more slots forinclusion of advertising content provided by the advertising system. Thecookie associated with the advertising system can be received from theresident device in association with processing an ad call that isincluded in the content that is retrieved from the publisher website.The received cookie can be used to locate other cookies associated withother browsers of the resident device and associated information foreach cookie related to user interactions of the user of the residentdevice. The located cookies can be used to determine relevant contentfor inclusion in the ad slot responsive to the ad call. The script caninclude a call to an operating system of the resident device to retrievethe unique identifier for the device. The unique identifier can beselected from the group comprising serial number, IMEI, MEID, ICCID,device identifier, IDFA, or advertising system identifier. The URL caninclude contextual information including one or more of an applicationidentifier, information related to the webview or other contextualinformation, or location information associated with the residentdevice. The contextual information can be used to select content toserve responsive to the received request. Passing can include providinga redirect to the publisher website that redirects an underlying adrequest to the publisher website from the advertising system. Passingthe cookie for the advertising domain can include calculating a cookiebased on the received unique identifier. Passing the cookie for theadvertising domain can include generating a pseudo random cookie, andstoring the generated pseudo random cookie indexed by the uniqueidentifier. The script can be provided to an application that includesthe webview.

Particular implementations may realize none, one or more of thefollowing advantages. Content customized for a user can be presented ina webview. Information related to interactions by the user with contentpresented in various webviews can be used for selecting contentsubsequently presented to the user, despite a cookie space associatedwith the webview possibly being cleared upon closure of the webview andthe cookie spaces of the various webviews being separate on the user'sdevice.

The details of one or more implementations of the subject matterdescribed in this specification are set forth in the accompanyingdrawings and the description below. Other features, aspects, andadvantages of the subject matter will become apparent from thedescription, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example environment for providingcontent to a user device.

FIG. 2 is a block diagram of an example system for expanding a cookiespace associated with a webview.

FIGS. 3A and 3B are sequence diagrams of an example process forexpanding a cookie space associated with a webview.

FIG. 4 is a flowchart of an example process for expanding a cookie spaceassociated with a webview.

FIG. 5 is a block diagram of computing devices that may be used toimplement the systems and methods described in this document, as eithera client or as a server or plurality of servers.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

A web browser can be used to display content available through theInternet. An application on a device can as well be adapted to displayweb content, such as by including an embedded web browser in theapplication. A webview is an application (e.g., a mobile application)that can display web content using for example an embedded browser. Aconventional webview application has its own cookie space which in somecases is not persistent—e.g., the cookie space can be cleared when theapplication ends, the application is re-installed, etc. This lack ofpersistency of the cookie space of the webview application poseschallenges for presenting user-customized content in the webview. Insome implementations proposed herein, the webview application (or ascript associated with the application) can be configured to provide aunique identifier for a hosting mobile device and to receive a cookieassociated with the domain of a content serving (e.g., advertising)system. The received cookie can be associated with user interactioninformation and the user interaction information can be used to selectcontent to present to the user in the webview application (hereinafter,just webview), in a second, different webview, in a browser, or inanother application, to name a few examples.

For situations in which the systems discussed here collect informationabout users, or may make use of information about users, the users maybe provided with an opportunity to control whether programs or featurescollect user information (e.g., information about a user's socialnetwork, social actions or activities, profession, demographics, auser's preferences, or a user's current location), or to control whetherand/or how to receive content from a content server that may be morerelevant to the user. In addition, certain data may be treated in one ormore ways before it is stored or used, so that certain information aboutthe user is removed. For example, a user's identity may be treated sothat no identifying information can be determined for the user, or auser's geographic location may be generalized where location informationis obtained (such as to a city, ZIP code, or state level), so that aparticular location of a user cannot be determined. Thus, the user mayhave control over how information about the user is collected and usedby a content server.

FIG. 1 is a block diagram of an example environment 100 for providingcontent to a user device. The example environment 100 includes a network102, such as a local area network (LAN), a wide area network (WAN), theInternet, or a combination thereof. The network 102 connects websites104, user devices 106, content sponsors 108, publishers 109, a contentmanagement system 110, application developers 111, and a search system113. The example environment 100 may include many thousands of websites104, user devices 106, and content sponsors 108. The content managementsystem 110 may be used for selecting and providing content in responseto requests for content. The content sponsors 108 can be, for example,advertisers. Other types of content sponsors are possible.

A content sponsor 108 can create a content campaign associated with oneor more content items using tools provided by the content managementsystem 110. For example, the content management system 110 can provideone or more account management user interfaces for creating and managingcontent campaigns. The account management user interfaces can be madeavailable to the content sponsor 108, for example, either through anonline interface provided by the content management system 110 or as anaccount management software application installed and executed locallyat a content sponsor's client device.

A content sponsor 108 can, using the account management user interfaces,provide campaign parameters which define a content campaign. The contentcampaign can be created and activated for the content sponsor 108according to the parameters specified by the content sponsor 108.Campaign parameters can include, for example, a campaign name, apreferred content network for placing content, a budget for thecampaign, start and end dates for the campaign, a schedule for contentplacements, content (e.g., creatives), bids, and selection criteria.Selection criteria can include, for example, a language, one or moregeographical locations or websites, and one or more selection terms.

A website 104 includes one or more resources 105 associated with adomain name and hosted by one or more servers. An example website 104 isa collection of web pages formatted in hypertext markup language (HTML)that can contain text, images, multimedia content, and programmingelements, such as scripts. Each website 104 can be maintained by acontent publisher, which is an entity that controls, manages and/or ownsthe website 104.

A resource 105 can be any data that can be provided over the network102. A resource 105 can be identified by a resource address that isassociated with the resource 105. Resources 105 include HTML pages, wordprocessing documents, portable document format (PDF) documents, images,video, applications, and news feed sources, to name only a few. Theresources 105 can include content, such as words, phrases, videos,images and sounds, that may include embedded information (such asmeta-information hyperlinks) and/or embedded instructions (such asscripts). A content sponsor 108 can act as a content publisher and canbe associated with a website 104, and with one or more resources 105(e.g., web pages, applications, other resources). Resources can beprovided by the publishers 109 or by the application developers 111, forexample.

A user device 106 is an electronic device that is under control of auser and is capable of requesting and receiving resources 105 over thenetwork 102. Example user devices 106 include personal computers, tabletcomputers, mobile communication devices (e.g., smartphones),televisions, set top boxes, personal digital assistants and otherdevices that can send and receive data over the network 102. A userdevice 106 typically includes one or more user applications, such as aweb browser, to facilitate the sending and receiving of data over thenetwork 102. The web browser can interact with various types of webapplications, such as a game, a map application, or an e-mailapplication, to name a few examples.

A user device 106 can request resources 105 from a website 104. In turn,data representing the resource 105 can be provided to the user device106 for presentation by the user device 106. User devices 106 can alsosubmit search queries to the search system 113 over the network 102. Inresponse to a search query, the search system 113 can, for example,access an indexed cache 114 to identify resources 105 that are relevantto the search query. The search system 113 identifies the resources 105in the form of search results and returns the search results to the userdevices 106 in search results pages. A search result is data generatedby the search system 113 that identifies a resource 105 that isresponsive to a particular search query, and can include a link to theresource 105. An example search result can include a web page title, asnippet of text or a portion of an image extracted from the web page,and the URL (Unified Resource Location) of the web page.

A search result or a resource 105 can be sent responsive to a requestreceived from a user device 106. The search result or resource 105 canbe sent with a request for the web browser of the user device 106 to seta Hypertext Transfer Protocol (HTTP) cookie. A cookie can represent, forexample, a particular user device 106 and/or a particular web browser.For example, the search system 113 can include a server that replies toa search query by sending a search result in an HTTP response. Such anHTTP response can include instructions (e.g., a set cookie instruction)requesting the browser to store a cookie for the site hosted by theserver.

In some implementations, each cookie can include content which specifiesan initialization time that indicates a time at which the cookie wasinitially set on the particular user device 106. If the browser supportscookies and cookies are enabled, subsequent page requests to the sameserver can include the cookie for that server. Because HTTP is astateless protocol, the use of cookies can allow an external service,such as the search system 113, the content management system 110 orother system, to track particular actions and status of a user overmultiple sessions. The cookie can store a variety of data, and in someimplementations, a unique or semi-unique identifier. In someimplementations, the identifier can be anonymized so that the privacy ofusers is protected. For example, in some implementations, semi-uniqueidentifiers are associated with users, but actual identifyinginformation of the users is not stored in a cookie. Additionally, insome implementations any identified user interactions can be generalizedrather than associated with a particular user. Encryption andobfuscation techniques can also be used to protect the privacy of users.

The data representing the resource 105 or the search results can alsoinclude data specifying a portion of the resource 105 or search resultsor a portion of a user display (e.g., a presentation location of apop-up window or in a slot of a web page) in which other content (e.g.,advertisements) can be presented. These specified portions of theresource or user display are referred to as slots or impressions. Anexample slot is an advertisement slot.

When a resource 105 or search results are requested by a user device106, the content management system 110 may receive a request for contentto be provided with the resource 105 or search results. The request forcontent can include characteristics of one or more slots or impressionsthat are defined for the requested resource 105 or search results. Forexample, a reference (e.g., URL) to the resource 105 or search resultsfor which the slot is defined, a size of the slot, and/or media typesthat are available for presentation in the slot can be provided to thecontent management system 110. Similarly, keywords associated with arequested resource 105 or a search query for which search results arerequested can also be provided to the content management system 110 tofacilitate identification of content that is relevant to the resource105 or search query. An identifier (e.g., cookie) associated with theuser device 106 can be received with the request for content.

Based, for example, on data included in the request for content, thecontent management system 110 can select content items that are eligibleto be provided in response to the request. One or more selected contentitems 114 can be provided to the user device 106 in association withproviding an associated resource 105 or search results. The providedcontent item(s) can be presented on the user device 106, in one or morerespective slots.

In some implementations, the content management system 110 can selectcontent items based at least in part on results of an auction. Forexample, content sponsors 108 can provide bids specifying amounts thatthe content sponsors 108 are respectively willing to pay forpresentation of their content items. In turn, an auction can beperformed and the slots can be allocated to content sponsors 108according, among other things, to their bids and/or the relevance of acontent item to content presented on a page hosting the slot or arequest that is received for the content item. For example, when a slotis being allocated in an auction, the slot can be allocated to thecontent sponsor 108 that provided the highest bid or a highest auctionscore (e.g., a score that is computed as a function of a bid and/or aquality measure). When multiple slots are allocated in a single auction,the slots can be allocated to a set of bidders that provided the highestbids or have the highest auction scores.

An application provided by an application developer 111 can include oneor more embedded browsers. A webview that is implemented as or thatincludes the embedded browser can be used, for example, to present aresource 105 (e.g., web page) associated with a publisher 109 to arequesting user device 106. In some implementations, the applicationdeveloper 111 can be associated with the publisher 109. For example, theapplication developer 111 can develop a mobile application for thepublisher 109 for purposes of presenting publisher content 116 on theuser device 106. The publisher 109 may desire to present the content ofthe publisher web page in the application without needing to modify thepublisher web page or without requiring the user to open a genericbrowser and navigate to a resource associated with the publisher 109. Awebview can facilitate such presentation.

A conventional webview can have a temporary cookie space, meaning thatthe cookie space for the webview can be cleared when the application(and correspondingly, the embedded browser) closes. To overcome a lackof cookie persistency in the webview, the application (or a scriptprovided to the application) can be configured to retrieve a uniqueidentifier associated with the user device 106, encode the uniqueidentifier, construct a URL that includes a domain associated with thecontent management system 110, and pass the encoded unique identifier(e.g., identifier 118) to the content management system 110. Details ofthis process are described in further detail below.

The content management system 110 can, in response to receiving theencoded unique identifier, pass a cookie for the domain associated withthe content management system 110 back to the webview for inclusion inthe cookie space of the webview. The application (or a script providedto the application) can be configured to make a second call afterreceipt of the cookie to the publisher website to retrieve content fromthe publisher website for inclusion in the webview (without modifyingthe publisher content). Subsequent calls to the content managementsystem 110 from the webview can include the cookie. Subsequent calls caninclude, for example, requests for content for content slots included inthe publisher content and notifications of user interactions withpresented content.

The content management system 110 can pass a same cookie to the userdevice 106 in response to receiving the encoded unique identifier fromother webviews running on the same user device 106, such as from asecond instance of the webview in a later, different session, or from asecond, different webview (e.g., included in the same or a differentapplication). Subsequent calls to the content management system 110 fromthe other webviews can include the cookie.

The content management system 110 can store, in a repository 120, inassociation with the unique identifier, information related tointeractions of a user of the user device 106 when accessing content onthe web through different browsers, including information related tointeractions with two or more of the webview and/or with a second,different webview. When the content management system 110 identifies arequest for content as being associated with the user device 106, thecontent management system 110 can retrieve the interaction informationand use the interaction information to determine content for deliveryresponsive to the request.

In some implementations, a unique identifier associated with a userdevice 106 can be re-set (e.g., in response to user action or some otherevent). The content management system 110 can receive a request with thenew unique identifier and can determine that the new unique identifiercorresponds to a previously stored unique identifier. The contentmanagement system 110 can associate a cookie previously associated withthe previously stored unique identifier with the new unique identifier.

FIG. 2 is a block diagram of an example system 200 for expanding acookie space associated with a webview. A user uses a user device 202 toview various user interfaces, including user interfaces 204, 206 and208. The user interface 204 includes an application 210 which is a“NewsX” application. The application 210 includes a webview browser 212,which can be used to present content from a “NewsX.com” website in theapplication 210. The user interface 206 includes an application 213which is a second instance of the NewsX application executing on theuser device 202 at a time after the application 210 is closed. Theapplication 213 includes a webview browser 214 which is a second,different instance of the webview browser 212. The user interface 208includes a different, weather-related application 215. The application215 includes a webview browser 216.

The application 210 sends a request to an operating system of the userdevice 202 to retrieve a unique identifier associated with the userdevice 202. The request can be initiated based on a script that isincluded in the application 210. In some implementations, theapplication 210 constructs a URL (Uniform Resource Locator) thatincludes the unique identifier and a domain associated with a contentserver 217. In some implementations, the application 210 can includeother information in the URL, such as an application identifier and/orlocation information for the user device 202 (or other contextualinformation). While reference is made to constructing a URL, other formsof message are possible.

The application 210 prompts the webview browser 212 to load the URL. Inresponse to the prompt from the application 210, the webview browser 212sends an HTTP (HyperText Transfer Protocol) request to the contentserver 217. In response to the HTTP request, the content server 217generates a cookie and includes the cookie in an HTTP response sent tothe webview browser 212. The content server 217 can store the cookie, inassociation with the received device identifier (after the deviceidentifier is extracted from the received URL), in a repository 218(e.g., as illustrated by “Device1/cookie1” information included in arepository entry 219 a). The repository 218 can also include information(e.g., an entry 219 b) associated with other devices (e.g., otherdevices associated with the user of the user device 202 or with otherusers).

The webview browser 212 stores the cookie (e.g., “cookie1”) in a cookiearea 220 associated with the webview browser 212 that is included incookie storage 221 of the user device 202. The cookie storage 221 alsoincludes cookie areas 222 and 224 associated with the webview browsers214 and 216, respectively, and a cookie area 226 associated with abrowser (e.g., a non-webview browser) of the user device 202. Aconventional webview browser can access cookies in its own cookie spacebut cannot access cookies in other cookie spaces. For example, in someimplementations, the webview browser 212 can access the cookie space 220but cannot access the cookie spaces 222, 224, or 226. In someimplementations, the cookie spaces 220 and 222 associated with the NewsXapplication are in a shared cookie space.

After prompting the webview browser 212 to load the URL, the application210 prompts the webview browser 212 to load the NewsX.com publisherpage. The webview browser 212 sends a request for the publisher page toa server associated with the publisher (not shown). The publisher serverprovides the NewsX.com page to the user device 202 and the NewsX.compage is rendered in the webview browser 212. In this example, whenrendering the NewsX.com page, the webview browser 212 encounters acontent slot 228 included in the NewsX.com page.

The content slot 228 can be associated with a script which, whenexecuted, sends a request to the content server 217 for a content itemto present in the content slot 228. The content server 217 can select acontent item for the content slot 228, such as based on content ormetadata associated with the NewsX.com web page, contextual informationincluded in the URL provided by the application 210, other contextualinformation, or other information known by the content server 217. Theselected content item is provided to the webview browser 212, forpresentation in the content slot 228, as illustrated by a content item230.

The user of the user device 202 can interact with the presented contentitem 230 (e.g., select the content item 230), which can result in alanding page of the content item 230 being presented in the webviewbrowser 212 (or in another browser, such as a default, e.g.,non-embedded browser installed on the user device 202). The user canpurchase a product or perform some other action which may be determinedto be a conversion. Conversion/interaction information can be sent fromthe webview browser 212 to the content server 217, for storage in therepository 218. For example, the entry 219 a includes“App1-interaction1” information. When the URL generated by theapplication 210 and provided to the webview browser 212 includescontextual information, contextual information can be stored in therepository 218, such as in association with the device identifier, thecookie provided to the webview browser 212, and/or with receivedinteraction information (e.g., the “App1” label included in the“App1-interaction1” information can indicate that the “interaction1”interaction was associated with the “NewsX” application 210).

In some implementations, upon closure of the application 210, the cookiearea 220 associated with the webview browser 212 is cleared. Asmentioned, the application 213 is a second instance of the application210 that is invoked at a time after the application 210 is closed. Whenthe application 213 is invoked by a user, the application 213 generates(or retrieves) a URL that includes the unique identifier associated withthe user device 202 and the domain associated with the content server217 (among possibly other information). As described above inassociation with the actions of application 210, the application 213prompts the webview browser 214 to load the URL. In response, thewebview browser 214 sends a request to the content server 217. Inresponse to the request from the webview browser 214 and based on thereceived unique identifier, the content server 217 retrieves (orregenerates) the previously generated cookie associated with the userdevice 202 and includes the cookie in a response sent to the webviewbrowser 214. The webview browser 214 stores the cookie (e.g., “cookie1”)in the cookie area 222.

After prompting the webview browser 214 to load the URL, the application213 prompts the webview browser 214 to load the NewsX.com publisherpage. The webview browser 214 sends a request for the publisher page tothe publisher server. The publisher server provides the NewsX.com pageand the NewsX.com page is rendered in the webview browser 214. Whenrendering the NewsX.com page, the webview browser 214 encounters acontent slot 232 included in the NewsX.com page. The processing of thecontent slot 232 results in a request for content being sent to thecontent server 217.

The request for content for the content slot 232 includes the cookieincluded in the cookie area 222. The content server 217 can locate theentry 219 a based on the received cookie. The content server 217 canselect a content item for the content slot 232 based at least in part oninformation in or associated with the entry 219 a (e.g., on informationassociated with prior interactions of the user with previous instancesof the webview browser 214). The selected content item is provided tothe webview browser 214, for presentation in the content slot 232, asillustrated by a content item 234. The user of the user device 202 caninteract with the presented content item 234 and conversion/interactioninformation (which includes the cookie provided to the webview browser214) can be sent from the webview browser 214 to the content server 217,for storage in the repository 218. For example, the entry 219 a includes“App1-interaction2” information. Upon closure of the application 213,the cookie area 222 associated with the webview browser 214 is cleared.

Similar to processing related to the webview browsers 212 and 214, thecontent server 217 can send a cookie to the webview browser 216, inresponse to a URL being provided to the content server 217 by thewebview browser 216 (e.g., in association with initiation of theunderlying application). The cookie is stored in the cookie area 224associated with the webview browser 216. When the URL includes anapplication identifier (e.g., “App2” corresponding to the weatherapplication), the application identifier can be stored in or associatedwith the entry 219 a. The application 215 can prompt the webview browser216 to load a publisher page (e.g., “WeatherX.com”) and the publisherpage can be rendered in the webview browser 216, which can result in acontent request being sent to the content server 217 for a content slot236.

The content request includes the cookie provided to the webview browser216. The content server 217 can select a content item for the contentrequest based on information in or associated with the entry 219 a(e.g., based on interactions associated with webview browsers that aredifferent than the webview browser 216). The selected content item isprovided to the webview browser 216, for presentation in the contentslot 236, as illustrated by a content item 238. When the user interactswith the content item 238, interaction information can be sent to thecontent server 217 and stored in or associated with the entry 219 a(e.g., the entry 219 a includes “App2-interaction1” information).

Information in or associated with the entry 219 a can be used to selectcontent for other requests for content. For example, information in orassociated with the entry 219 a can be used to select a content item 240that is presented in the application 215. The content server 217 canidentify the entry 219 a, for example, based on an applicationidentifier or a device identifier included in the content request, andbased on this identification can provide content in application 215 thatrelates to other content or interactions that occurred in otherapplications or in association with another browser.

FIG. 3A is a sequence diagram of an example process 300 for expanding acookie space associated with a webview. A first application 302 runningon a mobile device sends a request 304 to a device service 306 runningon the mobile device for a device identifier associated with the mobiledevice. The device service 306 returns a device identifier 308 to thefirst application 302.

The first application 302 constructs a URL using the device identifier(310). The URL includes a domain associated with a content servingsystem 312.

The first application 302 creates or invokes a first webview browser314, for displaying web content from a first publisher 316 (318). Thefirst application 302 prompts (e.g., sends a request 320 to) the firstwebview browser 314 to load the URL constructed by the first application302.

In response to the prompt (e.g., receiving the request 320), the firstwebview browser 314 sends an HTTP request 322 to the content servingsystem 312. The HTTP request 322 includes the device identifier. Inresponse to receiving the HTTP request 322, the content serving system312 generates a cookie using the device identifier included in the HTTPrequest 322 (324). The content serving system 312 stores the cookie in arepository 326 (328).

The content serving system 312 generates an HTTP response that includesthe cookie (330) and sends the HTTP response to the first webviewbrowser 314 (332). The first webview browser 314 receives the HTTPresponse and stores the cookie included in the HTTP response in a cookiespace associated with the first webview browser 314 (334).

The first application 302 prompts (e.g., sends a request 336 to) thefirst webview browser 314 to load a first publisher web page associatedwith the first publisher 316. In response to the request 336, the firstwebview browser 314 sends a request 338 to the first publisher 316 forthe first publisher web page. The first publisher 316 sends the firstpublisher web page to the first webview browser 314 (340). The firstwebview browser 314 renders the first publisher web page (341).

When rendering the first publisher web page, the first webview browser314 encounters a content slot associated with the content serving system312. The first webview browser 314 sends a request 342 for content forthe slot to the content serving system 314. The request 342 includes thecookie stored by the first webview browser 314.

The content serving system 312 selects content in response to therequest 342 (343). The first webview browser 314 receives the contentfrom the content serving system 312 and renders the content (344).

Subsequent to the rendering of a content item received from the contentserving system 312, the first webview browser 314 receives and processesan indication of a user interaction with the content item (345). Thefirst webview browser 314 can, for example, execute a script provided bythe content serving system 312 and included in or otherwise associatedwith the content item. The first webview browser 312 sends anotification 346 which includes interaction data to the content servingsystem 312. The notification 346 includes the cookie previously storedby the first webview browser 314.

The content serving system 312 stores the interaction data in therepository 326, in association with the cookie (347). As described inmore detail below, the content serving system 312 can use the storedinteraction data when selecting content for subsequent requests forcontent that are associated with the same mobile device.

The first application 302 receives an indication that the firstapplication 302 is closing (348). As part of the closing of the firstapplication 302, the first webview browser 314 is closed (349). Theclosing of the first webview browser 314 includes the clearing of thecookie space associated with the first webview browser 314.

FIG. 3B is a sequence diagram illustrating a process 350 which is acontinuation of the example process 300 of FIG. 3A.

Upon initiation, a second application 352 on the mobile deviceconstructs a URL using a device identifier of the mobile device (354).The second application 352 may have previously retrieved the deviceidentifier, for example. The second application 352 creates or invokes asecond webview browser 356, for displaying web content from a secondpublisher 358 (360).

The second application 352 prompts (e.g., sends a request 362 to) thesecond webview browser 356 to load the URL constructed by the secondapplication 352. In response to the prompt (e.g., receiving the request362), the second webview browser 356 sends an HTTP request 364 to thecontent serving system 312. The HTTP request 364 includes the deviceidentifier.

The content serving system 312 uses the device identifier to retrieve orgenerate a cookie associated with the device identifier that waspreviously stored in the repository 326 (366). The content servingsystem 312 generates an HTTP response that includes theretrieved/generated cookie (368) and sends the HTTP response to thesecond webview browser 356 (370). The second webview browser 356receives the HTTP response and stores the cookie included in the HTTPresponse in a cookie space associated with the second webview browser356 (372).

The second application 352 prompts (e.g., sends a request 374 to) thesecond webview browser 356 to load a second publisher web pageassociated with the second publisher 358. In response to the request374, the second webview browser 356 sends a request 376 to the secondpublisher 358 for the second publisher web page. The second publisher358 sends the second publisher web page to the second webview browser356 (378). The second webview browser 356 renders the second publisherweb page (380).

When rendering the second publisher web page, the second webview browser356 encounters a content slot associated with the content serving system312. The second webview browser 356 sends a request 382 for content forthe slot to the content serving system 312. The request 382 includes thecookie stored by the second webview browser 356.

The content serving system 312 retrieves interaction data associatedwith the cookie included in the request 382 from the repository 326(384). The content serving system 312 selects content in response to therequest 382 using the retrieved interaction data (386). The secondwebview browser 356 receives the content from the content serving system312 and renders the content (388).

Subsequent to the rendering of a content item received from the contentserving system 312, the second webview browser 356 receives andprocesses an indication of a user interaction with the content item(390). The second webview browser 356 can, for example, execute a scriptprovided by the content serving system 312 and included in or otherwiseassociated with the content item. The second webview browser 356 sends anotification 392 which includes interaction data to the content servingsystem 312. The notification 392 includes the cookie previously storedby the second webview browser 356. The content serving system 312 storesthe interaction data in the repository 326, in association with thecookie (394).

The content serving system 312 can use the stored interaction data whenselecting content for subsequent requests for content that areassociated with the same mobile device. For example, a request forcontent can be received from the second webview browser 356 in a samesession as the session in which the request 382 is sent or in adifferent session (e.g., a subsequent session in which a second,different instance of the second webview browser 356 is generated). Asanother example, the content serving system 312 can use the storedinteraction data to select content in response to a subsequent requestreceived from a second instance of the first webview browser 314. As yetanother example, the content serving system 312 can use the storedinteraction data to select content in response to a subsequent requestreceived from a standalone browser (e.g., a browser that is not embeddedin an application) executing on the mobile device.

FIG. 4 is a flowchart of an example process 400 for expanding a cookiespace associated with a webview. The process 400 can be performed, forexample, by the content management system 110 described above withrespect to FIG. 1 or the content server 217 described above with respectto FIG. 2.

A webview is identified (402). In some implementations, the webview isan embedded browser and is associated with a cookie space and a pathdefinition that defines a publisher website that is to be loaded by thewebview.

A script is provided for execution when the webview is initiated (404).The script causes a resident device associated with the webview toretrieve a unique identifier associated with the resident device, insome implementations, encode the unique identifier, construct a URL thatincludes an advertising domain of an advertising system and the encodedunique identifier, and pass the encoded unique identifier to theadvertising system. The script can be configured to make a first call tothe advertising system, the first call including the encoded uniqueidentifier and an address for the advertising domain.

In some implementations, the unique identifier is encoded duringtransport to the advertising system, such as using the HTTPS protocol(Hyper Text Transfer Protocol Secured). In some implementations, thescript is provided to and executed in an application that includes thewebview. The script can include a call to an operating system, aservice, or a background process of the resident device to retrieve theunique identifier for the device. The unique identifier can be, forexample, a serial number, IMEI (International Mobile Station EquipmentIdentity), MEID (Mobile Equipment Identifier), ICCID (Integrated CircuitCard ID), IDFA (Identifier for Advertising), Android™ Advertising ID,some other device identifier, or an advertising system identifier. Insome implementations, the URL includes contextual information includingone or more of an application identifier, information related to thewebview or other contextual information, or location informationassociated with the resident device. In some implementations, passingincludes providing a redirect to the publisher website that redirectsfrom the advertising system to the publisher website.

Responsive to receipt of the encoded unique identifier by theadvertising system, a cookie for the advertising domain is passed backto the webview for inclusion in the cookie space of the webview (406).For example, the cookie can include the encoded unique identifier. Asanother example, the advertising system can generate the cookie bycalculating a cookie based on the received unique identifier. As yetanother example, the advertising system can generate a pseudo randomcookie and store the generated pseudo random cookie indexed by theunique identifier. The advertising system can, in response to receivingthe encoded unique identifier (e.g., in response to the first call),generate an empty response (e.g., a 1×1 transparent tracking pixel)which includes the cookie (e.g., the cookie of the advertising systemcan be dropped in the cookie space associated with the webview).

Information related to interactions of a user of the resident devicewhen accessing content on the web through different browsers orapplications is stored in a repository of the advertising system and inassociation with the unique identifier (408). The stored informationincludes information related to interactions with two or more sessionsof the webview, a second, different webview on the resident device, abrowser on the resident device, or an application on the residentdevice. Storing can include unifying the cookie spaces of the differentbrowsers, such as by associating the interaction information from eachof the different browsers with the unique identifier.

A request for content as being associated with the resident device isidentified (410). The request for content includes the cookie. Therequest for content can be for content to present in a second, differentwebview, a different instance of the webview (e.g., in a subsequentsession), a browser (e.g., not embedded in an application) on theresident device, or an application on the resident device. As anotherexample, the request for content can be for content to present in thewebview in the current session. As yet another example, the request forcontent can be for content to present in a second webview in the currentsession (e.g., an application can include two webviews).

For example, the script can be configured to make a second, differentcall after receipt of the cookie of the advertising system. The secondcall can be a call to the publisher website to retrieve content from thepublisher website for inclusion in the webview. The webview can renderthe retrieved publisher content. The publisher website can include oneor more slots for inclusion of advertising content provided by theadvertising system. The advertising system can receive, from theresident device, in association with processing, an ad call that isincluded in the content that is retrieved from the publisher website.The cookie associated with the advertising system can be included in thead call. The advertising system can use the received cookie to locateinformation related to user interactions of the user of the residentdevice related to the webview. As another example, the advertisingsystem can use the received cookie to locate other cookies associatedwith other browsers of the resident device and associated informationfor each cookie related to user interactions of the user.

The information is used to determine content for delivery responsive tothe request (412). The advertising system can use the located cookiesand the associated interaction information to determine relevant contentfor inclusion in the ad slot responsive to the ad call. When the URLincludes contextual information, the contextual information can be usedto select content to serve responsive to the received request.

Contextual information can be analyzed for a user across multipleapplications and future content selection can be based on the analysis.For example, information stored for a user can indicate that the userhas used a first application (e.g., a travel-related application) and asecond application (e.g., a sports-related application) on the userdevice of the user. A subsequent request for content received from theuser device can be served based on the analysis of the user's use of themultiple applications on the user device (e.g., a content item relatedto both sports and travel can be selected).

Contextual information across users can be analyzed and future contentselection can be based on the analysis. For example, when an applicationidentifier is passed for a particular application, user interactioninformation related to that application associated with multiple userscan be stored and analyzed. Subsequent content selection for a requestfor content associated with the application can be based on theinformation analyzed for the multiple users, in addition to or as analternative to analyzing information associated with the user associatedwith the request.

In some implementations, in response to a request for content, a contentitem is provided which includes a tracking pixel or script. When thecontent item is rendered in the webview, the tracking pixel or scriptcalls back to the advertising system for the advertising system to dropa cookie associated with the advertising system into a cookie spaceassociated with the webview. The cookie can be included in and used forselecting content for subsequent requests for content received by theadvertising system.

FIG. 5 is a block diagram of computing devices 500, 550 that may be usedto implement the systems and methods described in this document, aseither a client or as a server or plurality of servers. Computing device500 is intended to represent various forms of digital computers, such aslaptops, desktops, workstations, personal digital assistants, servers,blade servers, mainframes, and other appropriate computers. Computingdevice 550 is intended to represent various forms of mobile devices,such as personal digital assistants, cellular telephones, smartphones,and other similar computing devices. The components shown here, theirconnections and relationships, and their functions, are meant to beillustrative only, and are not meant to limit implementations of theinventions described and/or claimed in this document.

Computing device 500 includes a processor 502, memory 504, a storagedevice 506, a high-speed interface 508 connecting to memory 504 andhigh-speed expansion ports 510, and a low speed interface 512 connectingto low speed bus 514 and storage device 506. Each of the components 502,504, 506, 508, 510, and 512, are interconnected using various busses,and may be mounted on a common motherboard or in other manners asappropriate. The processor 502 can process instructions for executionwithin the computing device 500, including instructions stored in thememory 504 or on the storage device 506 to display graphical informationfor a GUI on an external input/output device, such as display 516coupled to high speed interface 508. In other implementations, multipleprocessors and/or multiple buses may be used, as appropriate, along withmultiple memories and types of memory. Also, multiple computing devices500 may be connected, with each device providing portions of thenecessary operations (e.g., as a server bank, a group of blade servers,or a multi-processor system).

The memory 504 stores information within the computing device 500. Inone implementation, the memory 504 is a computer-readable medium. Thecomputer-readable medium is not a propagating signal. In oneimplementation, the memory 504 is a volatile memory unit or units. Inanother implementation, the memory 504 is a non-volatile memory unit orunits.

The storage device 506 is capable of providing mass storage for thecomputing device 500. In one implementation, the storage device 506 is acomputer-readable medium. In various different implementations, thestorage device 506 may be a floppy disk device, a hard disk device, anoptical disk device, or a tape device, a flash memory or other similarsolid state memory device, or an array of devices, including devices ina storage area network or other configurations. In one implementation, acomputer program product is tangibly embodied in an information carrier.The computer program product contains instructions that, when executed,perform one or more methods, such as those described above. Theinformation carrier is a computer- or machine-readable medium, such asthe memory 504, the storage device 506, or memory on processor 502.

The high speed controller 508 manages bandwidth-intensive operations forthe computing device 500, while the low speed controller 512 manageslower bandwidth-intensive operations. Such allocation of duties isillustrative only. In one implementation, the high-speed controller 508is coupled to memory 504, display 516 (e.g., through a graphicsprocessor or accelerator), and to high-speed expansion ports 510, whichmay accept various expansion cards (not shown). In the implementation,low-speed controller 512 is coupled to storage device 506 and low-speedexpansion port 514. The low-speed expansion port, which may includevarious communication ports (e.g., USB, Bluetooth®, Ethernet, wirelessEthernet) may be coupled to one or more input/output devices, such as akeyboard, a pointing device, a scanner, or a networking device such as aswitch or router, e.g., through a network adapter.

The computing device 500 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 520, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 524. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 522. Alternatively, components from computing device 500 may becombined with other components in a mobile device (not shown), such asdevice 550. Each of such devices may contain one or more of computingdevice 500, 550, and an entire system may be made up of multiplecomputing devices 500, 550 communicating with each other.

Computing device 550 includes a processor 552, memory 564, aninput/output device such as a display 554, a communication interface566, and a transceiver 568, among other components. The device 550 mayalso be provided with a storage device, such as a microdrive or otherdevice, to provide additional storage. Each of the components 550, 552,564, 554, 566, and 568, are interconnected using various buses, andseveral of the components may be mounted on a common motherboard or inother manners as appropriate.

The processor 552 can process instructions for execution within thecomputing device 550, including instructions stored in the memory 564.The processor may also include separate analog and digital processors.The processor may provide, for example, for coordination of the othercomponents of the device 550, such as control of user interfaces,applications run by device 550, and wireless communication by device550.

Processor 552 may communicate with a user through control interface 558and display interface 556 coupled to a display 554. The display 554 maybe, for example, a TFT LCD display or an OLED display, or otherappropriate display technology. The display interface 556 may compriseappropriate circuitry for driving the display 554 to present graphicaland other information to a user. The control interface 558 may receivecommands from a user and convert them for submission to the processor552. In addition, an external interface 562 may be provide incommunication with processor 552, so as to enable near areacommunication of device 550 with other devices. External interface 562may provide, for example, for wired communication (e.g., via a dockingprocedure) or for wireless communication (e.g., via Bluetooth or othersuch technologies).

The memory 564 stores information within the computing device 550. Inone implementation, the memory 564 is a computer-readable medium. In oneimplementation, the memory 564 is a volatile memory unit or units. Inanother implementation, the memory 564 is a non-volatile memory unit orunits. Expansion memory 574 may also be provided and connected to device550 through expansion interface 572, which may include, for example, aSIMM card interface. Such expansion memory 574 may provide extra storagespace for device 550, or may also store applications or otherinformation for device 550. Specifically, expansion memory 574 mayinclude instructions to carry out or supplement the processes describedabove, and may include secure information also. Thus, for example,expansion memory 574 may be provide as a security module for device 550,and may be programmed with instructions that permit secure use of device550. In addition, secure applications may be provided via the SIMMcards, along with additional information, such as placing identifyinginformation on the SIMM card in a non-hackable manner.

The memory may include for example, flash memory and/or MRAM memory, asdiscussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 564, expansionmemory 574, or memory on processor 552.

Device 550 may communicate wirelessly through communication interface566, which may include digital signal processing circuitry wherenecessary. Communication interface 566 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 568. In addition, short-range communication may occur, suchas using a Bluetooth, WiFi, or other such transceiver (not shown). Inaddition, GPS receiver module 570 may provide additional wireless datato device 550, which may be used as appropriate by applications runningon device 550.

Device 550 may also communication audibly using audio codec 560, whichmay receive spoken information from a user and convert it to usabledigital information. Audio codex 560 may likewise generate audible soundfor a user, such as through a speaker, e.g., in a handset of device 550.Such sound may include sound from voice telephone calls, may includerecorded sound (e.g., voice messages, music files, etc.) and may alsoinclude sound generated by applications operating on device 550.

The computing device 550 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 580. It may also be implemented as part of asmartphone 582, personal digital assistant, or other similar mobiledevice.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back-end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front-end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back-end, middleware, orfront-end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), and theInternet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

A number of embodiments of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the invention. Forexample, various forms of the flows shown above may be used, with stepsre-ordered, added, or removed. Also, although several applications ofthe payment systems and methods have been described, it should berecognized that numerous other applications are contemplated.Accordingly, other embodiments are within the scope of the followingclaims.

What is claimed is:
 1. A method for expanding a cookie space of awebview comprising: obtaining, by a content management system and from afirst webview of a first application that is executing a script at aresident device, a URL that includes a unique identifier of the residentdevice; responsive to receipt of the unique identifier by the contentmanagement system: generating, by the content management system, acookie; dropping, by the content management system, the cookie in afirst temporary cookie space of the first webview; and storing, in arepository of the content management system, an entry that links thecookie and the unique identifier; after dropping the cookie in the firsttemporary cookie space of the first webview, receiving, from theresident device, interaction information including the cookie andspecifying activity taken within the first webview of the firstapplication; storing, in the entry that links the cookie and the uniqueidentifier, the interaction information received after dropping thecookie in the first temporary cookie space of the first webview, whereinthe first temporary cookie space is cleared when the first webview isclosed; after the first temporary cookie space of the first webview hasbeen cleared at the resident device, receiving, by the contentmanagement system and from a second different webview generated by theresident device, the URL that includes the unique identifier of theresident device; retrieving, by the content management system, thecookie from the entry using the unique identifier of the resident devicethat is included in the URL received from the second different webview;dropping, by the content management system, the retrieved cookie in asecond temporary cookie space of the second different webview;receiving, by the content management system and from the residentdevice, a request for presentation of a content item in a publisher pagebeing presented in the second different webview, wherein the requestincludes the retrieved cookie that was dropped in the second temporarycookie space; selecting, by the content management system and inresponse to the request, a content item for presentation in thepublisher page presented by the second different webview using theinteraction information received from the first webview that was storedin the entry that links the cookie and the unique identifier based onthe inclusion of the retrieved cookie that was dropped in the secondtemporary cookie space being included in the request; and providing theselected content item to the second different webview at the residentdevice.
 2. The method of claim 1 wherein the script is configured tomake a first call to the content management system, the first callincluding the unique identifier and an address for a domain of thecontent management system, and responsive to the first call, receive thecookie from the content management system for inclusion in the firsttemporary cookie space of the first webview.
 3. The method of claim 2wherein responsive to receipt of the first call, the content managementsystem is configured to provide a response, the method furthercomprising persisting the cookie across multiple different webviews eachhaving temporary cookie spaces that are cleared upon closure of thewebview.
 4. The method of claim 3 wherein the response includes atracking pixel.
 5. The method of claim 3, wherein the response is anempty response which includes no renderable content.
 6. The method ofclaim 1 wherein the script initiates a call to an operating system ofthe resident device to retrieve the unique identifier for the device. 7.The method of claim 1 wherein the unique identifier is one of a serialnumber, IMEI, MEID, ICCID, device identifier, IDFA, or contentmanagement system identifier.
 8. The method of claim 1 wherein the URLincludes contextual information including one or more of an applicationidentifier, information related to the first webview, or locationinformation for the resident device.
 9. The method of claim 8 furthercomprising using the contextual information to select the content itemto serve responsive to the received request.
 10. The method of claim 1further comprising generating the cookie including generating a pseudorandom cookie, and storing the generated pseudo random cookie indexed bythe unique identifier.
 11. The method of claim 1 wherein the script isprovided to the first application that includes the first webview.
 12. Anon-transitory computer-readable storage device storing instructionsthat, when executed by a processor, cause the processor to: obtain, froma first webview of a first application that is executing a script at aresident device, a URL that includes a unique identifier of the residentdevice; responsive to receipt of the unique identifier by the contentmanagement system: generate a cookie; drop the cookie in a firsttemporary cookie space of the first webview; and store, in a repositoryof the content management system, an entry that links the cookie and theunique identifier; after dropping the cookie in the first temporarycookie space of the first webview, receive, from the resident device,interaction information including the cookie and specifying activitytaken within the first webview of the first application; store, in theentry that links the cookie and the unique identifier, the interactioninformation received after dropping the cookie in the first temporarycookie space of the first webview, wherein the first temporary cookiespace is cleared when the first webview is closed; after the firsttemporary cookie space of the first webview has been cleared at theresident device, receiving, by the content management system and from asecond different webview generated by the resident device, the URL thatincludes the unique identifier of the resident device; retrieve thecookie from the entry using the unique identifier of the resident devicethat is included in the URL received from the second different webview;drop the retrieved cookie in a second temporary cookie space of thesecond different webview; receive, from the resident device, a requestfor presentation of a content item in a publisher page being presentedin the second different webview, wherein the request includes theretrieved cookie that was dropped in the second temporary cookie space;select, in response to the request, a content item for presentation inthe publisher page presented by the second different webview using theinteraction information received from the first webview that was storedin the entry that links the cookie and the unique identifier based onthe inclusion of the retrieved cookie that was dropped in the secondtemporary cookie space being included in the request; and provide theselected content item to the second different webview at the residentdevice.
 13. The product of claim 12 wherein: the script is configured tomake a first call to the content management system, the first callincluding the unique identifier and an address for a domain of thecontent management system, and responsive to the first call, receive thecookie from the content management system for inclusion in the firsttemporary cookie space of the first webview; and the instructions causethe processor to persist the cookie across multiple different webviewseach having temporary cookie spaces that are cleared upon closure of thewebview.
 14. The product of claim 12 wherein the script is configured tomake a second, different call after receipt of the cookie of the contentmanagement system, the second call to a first publisher website toretrieve content from the first publisher website for inclusion in thefirst webview.
 15. A system comprising: one or more processors; and oneor more memory elements including instructions that when executed causethe one or more processors to: obtain, from a first webview of a firstapplication that is executing a script at a resident device, a URL thatincludes a unique identifier of the resident device; responsive toreceipt of the unique identifier by the content management system:generate a cookie; drop the cookie in a first temporary cookie space ofthe first webview; and  store, in a repository of the content managementsystem, an entry that links the cookie and the unique identifier; afterdropping the cookie in the first temporary cookie space of the firstwebview, receive, from the resident device, interaction informationincluding the cookie and specifying activity taken within the firstwebview of the first application; store, in the entry that links thecookie and the unique identifier, the interaction information receivedafter dropping the cookie in the first temporary cookie space of thefirst webview, wherein the first temporary cookie space is cleared whenthe first webview is closed; after the first temporary cookie space ofthe first webview has been cleared at the resident device, receiving, bythe content management system and from a second different webviewgenerated by the resident device, the URL that includes the uniqueidentifier of the resident device; retrieve the cookie from the entryusing the unique identifier of the resident device that is included inthe URL received from the second different webview; drop the retrievedcookie in a second temporary cookie space of the second differentwebview; receive, from the resident device, a request for presentationof a content item in a publisher page being presented in the seconddifferent webview, wherein the request includes the retrieved cookiethat was dropped in the second temporary cookie space; select, inresponse to the request, a content item for presentation in thepublisher page presented by the second different webview using theinteraction information received from the first webview that was storedin the entry that links the cookie and the unique identifier based onthe inclusion of the retrieved cookie that was dropped in the secondtemporary cookie space being included in the request; and provide theselected content item to the second different webview at the residentdevice.
 16. The system of claim 15 wherein: the script is configured tomake a first call to the content management system, the first callincluding the unique identifier and an address for a domain of thecontent management system, and responsive to the first call, receive thecookie from the content management system for inclusion in the firsttemporary cookie space of the first webview; and the instructions causethe one or more processors to persist the cookie across multipledifferent webviews each having temporary cookie spaces that are clearedupon closure of the webview.